Using a Text Editor to Enter Dynamic Fading Settings

Dynamic fading scenario files can be created and edited with a text editor, created and edited with the included Excel editor, or created by any other software that can create a text file to the following specifications.

The scenario files are read by the software line-by- line. The software distinguishes between three different type of lines in the files.

Lines with "*" as the first character are directive lines. There are two directives: Columns and Channels.
All other lines are data lines. These lines contain the dynamic fading settings.
Blank lines and lines with "#" are ignored by the software. They can be used to improve readability and for comments.

Column Directives

The Columns directives specifies what settings are given in the file and the order in which they appear in the file. The Columns directive follows the format:

*Columns <setting_name1>, [<setting_name2>, [<setting_name3>]]

The valid setting names are "Delay", "Loss", and "UE Speed". The Columns directive may contain 1, 2, or 3 setting names in any order, separated by commas.

Fader Directives

The Fader directive specifies the start of a new fading channel (fader) in the definition, and how many paths are in the fader. The number of paths should be a whole number from 1 to 24.

*Fader Paths <number_of_paths>

Data Lines

Each data line consists of numeric values separated by commas that represent the state of the fader for a given amount of time.

Each state (row of fading data) may have a defined dwell time (seconds), delay (seconds), loss (dB), and speed (km/hr) values for up to 24 paths.

Dwell time, the first value, is the time that the dynamic fading engine should keep the fader in the state specified by the rest of the data line. A valid dwell time must be entered for each state. Dwell times are specified in seconds (between 0.01 s and 1000 s with a maximum resolution of 0.01 seconds).If a dwell time is missing, the firmware will display an error message when you download the file to the PXB.

Each additional value is one of the dynamic fading settings for one of the paths in the fader. All dynamic fading settings follow the same constraints as specified in the parameter definition for the respective path setting in the user interface.

Each line will have a number of settings equal to the number of setting names in the Columns directive times the number of paths specified in the Fader directive.

If two commas are adjacent or separated only by whites pace, then that value is considered blank. The software will use the value from the previous state for the setting corresponding to a blank value. If the first data row for a channel has a blank value, then the software will use the value for that setting as set in the user interface.

Example Dynamic Fading File Format

*Columns Delay, Loss, UE Speed
*Channel Paths 2
0.05, 4e-4, 0, 60, 7e-4, 10, 60
specifies that the first state of the first channel has two paths with a 50 ms dwell time:
Path 1 with a .4 ms delay, 0 dB loss, and 60 km/hr UE speed, and
Path 2 with a .7 ms delay, 10 dB loss and 60 km/hr UE speed.